Skip to content

Conversation

chrisbbreuer
Copy link
Member

@chrisbbreuer chrisbbreuer commented Aug 17, 2025

This PR contains the following updates:

npm

Package Change Age Adoption Passing Confidence
next (source) 14.0.0 -> 15.4.7 age adoption passing confidence

Release Notes

vercel/next.js (next)

14.0.0 -> 15.4.7

v15.4.2-canary.54

Compare Source

Core Changes

  • [Cache Components] Defer Request Data API resolution to another task in dev when it would suspend when prerendering: #82386
  • [devtool] migrate global inline style tag to css: #82778

Misc Changes

  • [turbopack] Update next docs with information about turbopack known adoption issues: #82560
  • Use jsx extension instead of js in global-error documentation: #82710
  • [sourcemaps] Fix sourcemapping in Redbox on Windows: #82078
  • [test] separate metadata font tests: #82746
  • Turbopack: don't look into fallback import map twice: #82786

Credits

Huge thanks to @lukesandberg, @gnoff, @cypherab01, @eps1lon, @huozhi, and @mischnic for helping!

Released by @nextjs-bot on 8/19/2025

v15.4.7

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • fix router handling when setting a location response header #82588

Credits

Huge thanks to @ztanner for helping!

Released by @ztanner on 8/18/2025

v15.4.2-canary.53

Compare Source

Core Changes

  • chore(test): update sharp api test: #82740
  • [type] dynamic skip generating unused types: #82755

Misc Changes

  • Turbopack: Stop persisting background task correctly on stop: #82727
  • Turbopack: fix race condition in test case: #82728
  • [turbopack] Remove a debug assertions in client references endpoint: #82725
  • Turbopack: use bail instead of panic: #82745
  • Update Rspack production test manifest: #82732
  • fix(turbopack): webpack-loaders failed to resolve relative path: #82720
  • create-next-app: use Turbopack for both dev and build: #82753
  • fix: make sure validator.ts uses relative paths for imports: #82761

Credits

Huge thanks to @sokra, @lukesandberg, @mischnic, @vercel-release-bot, @fireairforce, @wbinnssmith, @styfle, @huozhi, and @bgub for helping!

Released by @nextjs-bot on 8/18/2025


📊 Package Statistics

  • next: 13,016,663 weekly downloads

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Buddy 🤖

Copy link

pkg-pr-new bot commented Aug 17, 2025

Open in StackBlitz

npm i https://pkg.pr.new/stacksjs/launchpad/launchpad-installer@85
npm i https://pkg.pr.new/stacksjs/launchpad/@stacksjs/launchpad@85

commit: f589460

Copy link

netlify bot commented Aug 17, 2025

Deploy Preview for stacks-launchpad failed. Why did it fail? →

Name Link
🔨 Latest commit f589460
🔍 Latest deploy log https://app.netlify.com/projects/stacks-launchpad/deploys/68a4be542f66e2000825969b

@chrisbbreuer chrisbbreuer force-pushed the buddy-bot/update-major-update---next-1755454218107 branch 13 times, most recently from 065e7a4 to 702158b Compare August 18, 2025 20:08
@chrisbbreuer chrisbbreuer changed the title chore(deps): update dependency next to 15.4.6 chore(deps): update dependency next to 15.4.7 Aug 18, 2025
@chrisbbreuer chrisbbreuer force-pushed the buddy-bot/update-major-update---next-1755454218107 branch 10 times, most recently from cc8964d to f1aed75 Compare August 19, 2025 16:08
@chrisbbreuer chrisbbreuer force-pushed the buddy-bot/update-major-update---next-1755454218107 branch from f1aed75 to f589460 Compare August 19, 2025 18:11
@chrisbbreuer chrisbbreuer deleted the buddy-bot/update-major-update---next-1755454218107 branch August 19, 2025 18:12
@bgub
Copy link

bgub commented Aug 19, 2025

@chrisbbreuer any way to stop tagging contributors? The entire Next.js team is getting tagged with each PR 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants